|
VAIS001F
|
Initialization failed: insufficient storage - 01.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Unable to obtain storage for communication area.
|
| |
System action:
|
VAISMAIN terminates with condition code 64.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS002F
|
Build Data_Model failed: xxxxxxxx.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Problem encountered during a build of SequeLink configuration file, where xxxxxxxxxx describes the problem in more detail.
|
| |
System action:
|
The server abends with abend code 101.
|
| |
User response:
|
xxxxxxxx= 'VAISMNDM did not complete within time frame'. For all other reasons, contact DataDirect Technologies technical support.
|
|
VAIS005I
|
DB2 task started, DB2ifid(dddd).
|
| |
Severity:
|
Information
|
| |
Explanation:
|
DB2 root task started to support DB2 service for DB2ifid dddd.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS006E
|
DB2InterfaceId has an invalid length.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The maximum length of DB2InterfaceID is 4 characters.
|
| |
System action:
|
DB2 root task not started.
|
| |
User response:
|
Correct DB2InterfaceID.
|
|
VAIS007E
|
Problem building TACB for DB2ifid=xxxx.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
DB2 TACB could not be created.
|
| |
System action:
|
DB2 root task not started.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS008I
|
XTCP task started.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Extended TCP/IP listener task started.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS009F
|
Problem building XTCP TACB.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
XTCP TACB could not be created.
|
| |
System action:
|
The server abends with code 101.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS010F
|
No EntityList found.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
No EntityList was passed after SequeLink configuration file build-VAISMNDM.
|
| |
System action:
|
The server abends with code 101.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS011F
|
Active Agent failed: could not locate VAISMNDM on TACB chain.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
The server abends with code 102.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS012F
|
Specification error in SIL LOADTABL entry.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
The server abends with code 109.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS013E
|
DB2ifid xxxx matches a reserved OPRID.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Matches some predefined Operator Identifiers.
|
| |
System action:
|
DB2 root task not started.
|
| |
User response:
|
Change DB2ifid for this service.
|
|
VAIS014I
|
SMFrecording active, SMFrecordtype(nnn).
|
| |
Severity:
|
Information
|
| |
Explanation:
|
SMFrecording is activated.
|
| |
System action:
|
SMFrecordtype nnn will be written to SMF.
|
| |
User response:
|
None.
|
|
VAIS015I
|
SMFrecording active, tttttttttttttttttttttt.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
SMFrecording is not activated. Either you requested tttttttttttt=='No SMFrecordType specified' or you specified an invalid number, tttttttttt='SMFrecordType invalid range.'
|
| |
System action:
|
No SMF records will be written.
|
| |
User response:
|
None. To activate SMFrecording, correct the SMFrecordType. The value must be between 128 and 256.
|
|
VAIS016E
|
Error opening SYSCMDS file.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
An error occurred while opening SYSCMDS file.
|
| |
System action:
|
The Server continues initialization.
|
| |
User response:
|
Make sure the Server Userid is authorized to open SYSCMDS file. If problems persist, contact DataDirect Technologies technical support.
|
|
VAIS017I
|
Processing commands from SYSCMDS file.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The SYSCMDS file has been opened.
|
| |
System action:
|
The Server continues initialization.
|
| |
User response:
|
All commands in SYSCMDS will be processed.
|
|
VAIS018I
|
SosLimit above xxxxx K, below yyy K.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The MVSGlobalSosLimit attribute has reserved xxxxx KB of free storage above the 16 MB line. New connections will be refused when free storage drops below this limit.
In addition, yyy KB of free storage has been reserved below the 16 MB line, but this limit is fixed.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS021I
|
Running on ______ - _______.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The Operating System and Release on which the application is running are displayed.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS022I
|
CPUid(__) - CPUSerialNr __________ .
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The CPU id and CPU Serial number for all CPUs are displayed.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS023E
|
GETMAIN for TACB storage failed.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Insufficient storage left to allocate a TACB.
|
| |
System action:
|
STRTTHRD request fails.
|
| |
User response:
|
Increase Region size.
|
|
VAIS022I
|
CPUid(__) - CPUSerialNr __________ .
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The CPU id and CPU Serial number for all CPUs are displayed.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS024I
|
LX(nnnnnn) reserved.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
SequeLink reserved the following xxxxxx Linkage Index.
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS041I
|
Control CNTL Q message received.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
A control queue message was received by VAISMAIN.
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS051F
|
SIL configuration error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
The server abends.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS077E
|
Unrecognized service request.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Invalid service request from a server subtask.
|
| |
System action:
|
Server terminates abnormally with an abend code of U143.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS079E
|
Attach failed at Initialization time.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
VAISMAIN was unable to attach one of its subtasks.
|
| |
System action:
|
Server initialization continues. However, results are unpredictable.
|
| |
User response:
|
The z/OS server job log should contain a message (with the prefix CSV) indicating the reason for the attach failure. Report this error to DataDirect Technologies technical support.
|
|
VAIS084E
|
SERVER.MAIN error returned from @VAIOPR macro. RC = return code VC = verb code.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Logic error processing @VAIOPR request, resulting in the displayed return code and verb code.
|
| |
System action:
|
Request is ignored.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS085I
|
TASKNAME - TACBADDR - FLAGS - CPU - SERVICE - USERID.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The server is responding to a STATUS command. This is the header information about the tasks it is controlling. This message is the result of a CNTL STATUS command and is always followed by a VAIS089I message.
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS086I
|
Shutdown type(ttttttttt) initiated.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The server acknowledges shutdown where the type is either 'Immediate' or 'Normal'.
|
| |
System action:
|
System shutdown is initiated. If the shutdown is 'Normal', no new connections are allowed to start. The server will wait until all existing connections have ended normally before continuing Shutdown.
If the shutdown is 'Immediate', no new connections are allowed to start. Existing connections will be terminated in a consistent manner.
|
| |
User response:
|
Once you start a 'Normal' shutdown, you can overwrite it with an 'Immediate' shutdown.
|
|
VAIS087E
|
Invalid TYPE parameter on CLOSE command.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The value of the type parameter in the CNTL CLOSE command is invalid.
|
| |
System action:
|
The CNTL CLOSE command is ignored.
|
| |
User response:
|
Correct the parameter and issue the command again.
|
|
VAIS088T
|
Taskname xxxxxxxxxx Notified of shutdown.
|
| |
Severity:
|
Trace
|
| |
Explanation:
|
This is a debugging or trace message.
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS089I
|
taskname tacbaddr flags cputime service username.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message results from a CNTL STATUS command and is always preceded by a VAIS085I message. Each line of information includes the fields as titled by the VAIS085I header message. Each column provides information about a server task (server runtime component or application thread) and includes:
taskname - The name of the main line load module (server component task) or the thread ID of a z/OS application/service task.
tacbaddr - The address of the task's TACB. The TACB is the anchoring control block for all server tasks.
flags - A 4-byte set of flags representing the current status of the task. Flags can include:
p1:
D - dispatched
I - initializing
L - has a queue locked
W - wait state
X - exiting dispatcher
S - task is the SCT component
K - aborted by the SCT
p2: - Not used
p3:
T - task is an application thread
X - invalidated by the SCT
p4: - not used
cputime - CPU time consumed by the SequeLink engine task.
service - Usually, the name of the application (in the SYSINI) for an instance of the application thread. Alternatively, it is set to the literal '**CORE**' for all server component tasks.
username - Usually, the user ID that initiated this instance of the application thread. Alternatively, it is set to the literal '**Not applicable.**' for all server component tasks.
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS091F
|
xxxxxx task has ended unexpectedly - Abend server.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
An essential server component subtask has terminated.
|
| |
System action:
|
VAISMAIN terminates abnormally with an abend code of U146.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS095E
|
Alter request is invalid - invalid or missing keyword.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
This message is in response to a CNTL ALTER command. There are two possible causes:
- a keyword was not supplied.
- the keyword supplied was incorrect.
|
| |
System action:
|
The command is ignored.
|
| |
User response:
|
Check the syntax of the CNTL ALTER command. Verify that a correct keyword was included in the command. Refer to the SequeLink Administrator's Guide for details on the CNTL ALTER command.
|
|
VAIS100W
|
CellPool with CellSize(____) could not be expanded for Secondary Pages(_____).
|
| |
Severity:
|
Warning
|
| |
Explanation:
|
CellPool could not be expanded, probably due to a shortage of Virtual storage.
|
| |
System action:
|
None.
|
| |
User response:
|
Start up the Server with greater RegionSize, or contact DataDirect Technologies technical support.
|
|
VAIS101E
|
Function(________) failed Rc x''__'' in Thread(tttttttt), abend U079 will result.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
An internal error occurred due to a failure of the CellPool MemoryMgr function.
|
| |
System action:
|
Abend Thread tttttttt with U079.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS103I
|
Tttttttt - classified to WLMServiceClass(cccccccc)
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Threadid has been classified to WLMServiceClass(cccccccc).
|
| |
System action:
|
WLM will use workload appropriate to this ServiceClass when scheduling enclaves for this Thread.
|
| |
User response:
|
None.
|
|
VAIS110E
|
Tttttttt - IWMExxxx - WLM Returncode(returncode) Reasoncode (reasoncode)
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The WLM macro IWMExxxx returned a non-zero returncode or reasoncode, where IWMExxxx can be IWMECREA, IWMELEAV, IWMEJOIN, IWCLSFY, or IWMEDEL.
|
| |
System action:
|
Continue without enclave support for this thread.
|
| |
User response:
|
Check why this macro call failed. Contact DataDirect Technologies technical support.
|
|
VAIS111T
|
Tttttttt - IWMExxxx - WLMEnclaveToken(nnnnnnnn)
|
| |
Severity:
|
Trace
|
| |
Explanation:
|
Trace WLM macro IWMExxxx calls, show EnclaveToken where IWMExxxx can be IWMECREA, IWMELEAV, IWMEJOIN, IWCLSFY, or IWMEDEL.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS151F
|
SIL Start table missing.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
VAISMAIN could not locate the started tasks (STRTTABL).
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS152F
|
SIL NAME field error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
VAISMAIN could not locate a required START entry.
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS153F
|
SIL STKSIZE error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
The server has found an invalid STKSIZE value in one of the server's internal SIL entries.
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS154F
|
SIL DSASIZE error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Invalid DSASIZE value in one of the server's internal SIL entries.
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS155F
|
SIL AFLGS error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
There is an invalid AFLGS value in one of the server's internal SIL entries.
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS156F
|
SIL DPMOD error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
There is an invalid DPMOD value in one of the server's internal SIL entries.
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS157F
|
VAIT build error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Logic error while building the server VAIT list.
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS158F
|
VAIT OPRI error.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
Logic error while processing an OPERID entry in the SIL.
|
| |
System action:
|
VAISMAIN terminates with a condition code of 4.
|
| |
User response:
|
Report this error to DataDirect Technologies technical support.
|
|
VAIS159W
|
VAIBEAT - Error in DataModel, using default value for TimeInterval.
|
| |
Severity:
|
Warning
|
| |
Explanation:
|
TIMERINTERVAL incorrectly specified in SequeLink configuration file.
|
| |
System action:
|
A default TIMEINTERVAL of 15 seconds is set.
|
| |
User response:
|
Correctly specify TIMERINTERVAL in the SequeLink configuration file.
|
|
VAIS160F
|
No valid Service definitions in DataModel- at least 1 must be found.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
No valid service definition was found in the SequeLink configuration file. The Server requires at least one valid service definition.
|
| |
System action:
|
The server abends with abend U160.
|
| |
User response:
|
Correctly define a service in the SequeLink configuration file; then, call DataDirect Technologies technical support for assistance.
|
|
VAIS161E
|
Datamodel error for service xxxxxxxx, Service has been ignored.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
ServiceApplid was incorrectly specified in the SequeLink configuration file for service xxxxxx. The affected service will not be available until the error is corrected and the server is restarted.
|
| |
System action:
|
The incorrect service definition is ignored and bypassed.
|
| |
User response:
|
Correctly define ServiceApplid for service xxxxxxx in the SequeLink configuration file.
|
|
VAIS162E
|
DataModel ServiceIdleTime error, Service xxxxxxxx has been ignored.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
ServiceIdleTime was incorrectly specified in the SequeLink configuration file for service xxxxxx. The affected service will not be available until the error is corrected and the server is restarted.
|
| |
System action:
|
The incorrect service definition is ignored and bypassed.
|
| |
User response:
|
Correctly define ServiceIdleTime for service xxxxxxx in the SequeLink configuration file.
|
|
VAIS163W
|
DataModel ServiceIdleAction error, default set to MESSAGE for Service xxxxxxxx.
|
| |
Severity:
|
Warning
|
| |
Explanation:
|
ServiceIdleAction was incorrectly specified in the SequeLink configuration file for service xxxxxx. Default setting of MESSAGE will be used.
|
| |
System action:
|
The default value for the ServiceIdleAction parameter (MESSAGE) will be used.
|
| |
User response:
|
Correctly define ServiceIdleAction for service xxxxxxx in the SequeLink configuration file.
|
|
VAIS164E
|
DataModel ServiceMaxSession error, Service xxxxxxxx has been ignored.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
ServiceMaxSession was incorrectly specified in the SequeLink configuration file for service xxxxxx. The affected service will not be available until the error is corrected and the server is restarted.
|
| |
System action:
|
The incorrect service definition is ignored and bypassed.
|
| |
User response:
|
Correctly define ServiceMaxSession Time for service xxxxxxx in the SequeLink configuration file.
|
|
VAIS165I
|
Service list entry for service name (application name) built successfully - values:
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The SequeLink configuration file application service definitions for the named service representing the named application were successfully processed.
|
| |
System action:
|
The server's service list is updated with the named service (for example, the named application is available for use).
|
| |
User response:
|
None.
|
|
VAIS166E
|
Purged latch(es) for RequestorID(xxxxxxxx) RetCode(yy)
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Detach processing of a WorkerThread detected that one or more latches were still held.
|
| |
System action:
|
VAISMN purged all latches for this RequestorID.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS171E
|
LOAD failed for module xxxxxxxx with rc=zz -yyyyyyyy.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
A z/OS LOAD for loadmodule xxxxxxxx specified as ServiceApplid for yyyyyyyy failed with rc=zz. The affected service will not be available until this error is corrected and the Server restarted.
|
| |
System action:
|
The incorrect service definition is ignored and bypassed.
|
| |
User response:
|
Check why the loadmodule could not be accessed. Either ServiceApplid is a nonexistent loadmodule or z/OS Contents Supervisor detects errors. If problems persist, contact DataDirect Technologies technical support.
|
|
VAIS172E
|
STRTTHRD request for Service service_id from user_id at terminal_id, was not successful.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
An attempt to start an application thread failed. The affected application is identified by its name, the user by their user ID, and the terminal by its terminal ID. This message is always preceded by a VAIS174E or a VAIS175E message that details the reason for the failure.
|
| |
System action:
|
The application thread is not started.
|
| |
User response:
|
Check the preceding VAIS174E or VAIS175E message for the exact reason for failure. Respond accordingly.
|
|
VAIS173E
|
STRTTHRD request for Service service_id from user_id at terminal_id failed - SIL definition error.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
The application thread is not started.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS174E
|
Verification of STRTTHRD request for Service service_id from user_id at terminal_id failed - service definition was not found.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
The application thread is not started.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS175E
|
Verification of STRTTHRD request for Service service_id from user_id at terminal_id failed, xxxxxxxx.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
An attempt to start an application thread failed. The affected application is identified by its name, the user by their user ID, and the terminal by its terminal ID. The reason for the failure is also given. This message is always followed by a VAIS172E message.
|
| |
System action:
|
The application thread is not started.
|
| |
User response:
|
Respond to the reason given for the failure accordingly:
Not Active - the application service is not active; check for previous VAILOG messages relating to the application service and correct the error that prevented the successful validation and activation of the application service.
Stopped - an II or console operator stopped the application service with a CNTL ALTER command; restart the application service.
AtMaxsess - the maximum number of application threads for this application service was reached; increase this value by using the CNTL ALTER command or by changing the SYSINI MAXIMUMSESSIONS value in the application service definition.
Refer to the SequeLink Administrator's Guide for details regarding CNTL ALTER. Contact DataDirect Technologies technical support for details of the SIL definitions required for an application service.
|
|
VAIS176E
|
SIL section LOADTBL2 omitted.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
Server initialization continues.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS177E
|
NAME key omitted in LOADTBL2.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
Server initialization continues.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS178E
|
Syntax error in LOADTBL2/NAME.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
Server initialization continues.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS179I
|
xxxxxxxx normal end - Thrdid(yyyyyyyy).
|
| |
Severity:
|
Information
|
| |
Explanation:
|
A server task (an application thread or a server component) has ended with the stated condition code. If the task was an application thread, the thread identifier is also given in the message.
|
| |
System action:
|
The task is flushed from the system and all storage used by the task is freed.
|
| |
User response:
|
None. This message simply notes that a task has ended. This is a normal situation.
|
|
VAIS180I
|
xxxxxxxx abnormal end - cc(zzzz)- Thrdid(yyyyyyyy).
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Task ended abnormally. Either the task was deliberately aborted for Timeout or maxCPU reasons or by Operator commands, or otherwise suffered an abend.
zzzz = z/OS CompletionCode - Abendcode.
|
| |
System action:
|
None.
|
| |
User response:
|
None if the task was deliberately aborted. Otherwise, contact DataDirect Technologies technical support.
|
|
VAIS181I
|
Service: service name.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message is output following a CNTL STATUS command. It is always followed by a set of VAIS182I and VAIS183I messages. The service application for which the status was requested is identified by name. (The status is detailed in the subsequent VAIS182I and VAIS183I messages.)
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS182I
|
Application name = application name STATUS = xx DEBUG = flag.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message follows a VAIS181I message. It is output in response to a CNTL STATUS command. It reflects the current status (xx) of the named application service. This message also shows the setting of the DEBUG flag for the application service: this is Y (DEBUG is on) or N (DEBUG is off).
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
The fields in the message include:
xx - is a 1-byte, hexadecimal flag that shows the status for this application at startup time:
01 - service is active and available
02 - abort at time-out
04 - message only at time-out
08 - ignore time-outs
80 - service has been stopped by user
|
|
VAIS183I
|
MAXSESS = number CURRSESS = number TIMEOUT = value.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message follows a VAIS181I message. It is output in response to a CNTL STATUS command. It reflects the current values for the maximum number of sessions, the current number of sessions and the time-out value for the application service.
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS184E
|
** Show keyword is in error.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
This message is output in response to an incorrect CNTL STATUS command. It indicates that the SHOW= keyword in the command was not valid.
|
| |
System action:
|
The command is ignored.
|
| |
User response:
|
Use any of the following:
to control what data is displayed as a result of the CNTL STATUS command. Reenter the command with one of these keywords. Refer to the SequeLink Administrator's Guide for additional information regarding the CNTL STATUS command.
|
|
VAIS185E
|
** Error -- thread was not found.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
This message is output in response to an incorrect CNTL ABORT command. It indicates that the thread ID (THRDID=) specified in the command named an unknown thread.
|
| |
System action:
|
The command is ignored.
|
| |
User response:
|
Application service threads are tagged with a unique thread ID with the form: T#nnnnnn where nnnnnn is a decimal number.
Use the CNTL STATUS command to display the active application threads and reenter the command specifying a valid thread ID. Refer to the SequeLink Administrator's Guide for additional information regarding the CNTL STATUS and CNTL ABORT commands.
|
|
VAIS186E
|
** Error -- *USERID* or *THRDID* must be specified.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
This message is output in response to an incorrect CNTL ABORT command. The USERID= or THRDID= parameter was missing from the command string. At least one of these parameters is required in this command.
|
| |
System action:
|
The command is ignored.
|
| |
User response:
|
Correct the command and reenter it. Refer to the SequeLink Administrator's Guide for additional information regarding the CNTL ABORT command.
|
|
VAIS187E
|
** Error -- thread has already been aborted.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
This message is output in response to an incorrect CNTL ABORT command. It indicates that the operator is attempting to terminate abnormally an application service thread that has already been terminated abnormally.
|
| |
System action:
|
The command is ignored.
|
| |
User response:
|
Under certain circumstances, an ABORT of an application service thread instance can take about 3-10 seconds. Wait until this time has elapsed before attempting the command again.
|
|
VAIS188I
|
Thrdid(tttttttt) for User(uuuuuuuu) has been aborted.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message is output in response to a successful CNTL ABORT command. It indicates that the application service thread (identified by its thread ID) started by the stated user has been terminated abnormally.
|
| |
System action:
|
The affected thread is removed from the system and the associated application logic is terminated.
|
| |
User response:
|
None.
|
|
VAIS189T
|
ssssssss Service for User(uuuuuuuu) with Thrdid(tttttttt) exceeds Timeout value (xxxx/yyyy).
|
| |
Severity:
|
Trace
|
| |
Explanation:
|
An application service thread (identified by its thread ID) started by the stated user has exceeded the timeout value that was coded for the stated application in the SYSINI. The timeout value from the SYSINI is given together with the number of timer intervals that the thread has currently been inactive.
|
| |
System action:
|
Not applicable.
|
| |
User response:
|
None.
|
|
VAIS190W
|
WARNING Server thread for User(uuuuuuu) with Thrdid(tttttttt) at terminal (termid) exceeded Timeout value.
|
| |
Severity:
|
Warning
|
| |
Explanation:
|
An application service thread (identified by its thread ID) started by the stated user from the stated terminal has exceeded the timeout value that was coded for the application service being used. The value of the IDLEACTION (idle action) parameter in the SYSINI was set to MESSAGE, which causes an alert message to be displayed.
|
| |
System action:
|
Each time that the timeout value set for the application service elapses while the application service thread has been inactive (that is, no messages have been passed to the attached workstation), the server will produce an alert message.
|
| |
User response:
|
Investigate the cause of the application's inactivity. If desired, the thread might be terminated using the CNTL ABORT command.
|
|
VAIS191E
|
application name THREAD for USER user ID at THRDID (T#xxxxxx) at terminal ID aborted due to timeout.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
An application service thread (identified by its thread ID) started by the stated user from the stated terminal has exceeded the value that was coded for the application service being used by this thread. The value of the IDLEACTION (idle action) parameter in the SYSINI was set to ABORT. The server system has therefore abnormally terminated this thread.
|
| |
System action:
|
The named thread is terminated abnormally and removed from the server system.
|
| |
User response:
|
Investigate the cause of the application's inactivity. If need be, increase the IDLETIME value for the application service using the IDLETIME SYSINI parameter or the CNTL ALTER command. Contact DataDirect Technologies technical support for additional information regarding the CNTL ALTER command and the IDLETIME SYSINI parameter.
|
|
VAIS192E
|
application name THREAD for USER user ID at terminal ID -- not able to timeout abort.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
An application service thread (identified by its thread ID) started by the stated user from the stated terminal has exceeded the value that was coded for the application service being used by this thread. The value of the IDLEACTION (idle action) parameter in the SIL was set to ABORT, but the server was not able to abnormally terminate the thread.
|
| |
System action:
|
The thread cannot be terminated abnormally because of one of the following reasons:
- It is currently being terminated abnormally by an II or console operator command.
- It was never successfully started (generally an application link edit error).
- It has already ended.
|
| |
User response:
|
Use the CNTL STATUS command to check the current state of the thread. Verify that the application was built and linked correctly. Check the VAILOG for previous error messages relating to this thread (identified by its thread ID).
If necessary, contact DataDirect Technologies technical support.
|
|
VAIS193E
|
Error with ALTER command - service application was not found.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The operator (at a z/OS operator's console or at an II terminal) entered a CNTL ALTER command with an unknown service name.
|
| |
System action:
|
The command is ignored.
|
| |
User response:
|
Reenter the command (CNTL ALTER SERVICE=) and specify a valid service name. The CNTL STATUS SHOW=SERVICE command might be used to check the name of the target service.
|
|
VAIS194I
|
Alter services request was successful.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
The operator (at a z/OS operator's console or at an II terminal) entered a CNTL ALTER command to update an existing application service definition. The command was successful.
|
| |
System action:
|
The application service definition is updated according to the operator's specifications stated in the CNTL ALTER command.
|
| |
User response:
|
None.
|
|
VAIS195I
|
'Thrd(threadid) Stat(status) Type(type) Tcb(tcbad) RPCs(rpc) Cpu(cpu_used)
Threadid - Logon request from aaa.aaa.aaa.aaa for userid uuuuuuuu data source dddddddd
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message is a result of a logon command where:
threadId: Identifies the thread.
status: One of the following:
Busy: A thread is servicing an RPC.
Ready: A thread is waiting for RPCs to service.
Abort: A thread was forced to stop abnormally.
Creat: A thread is created.
Alloc: A thread is allocated.
Stopg: A thread is stopping.
Stopd: A thread is stopped.
type: P (permanent) or V (volatile). A permanent thread is started when the Server starts and is never stopped (the number of permanent threads equals the ServiceMinThread value.) A volatile thread is started when all permanent threads are busy, indicating a high workload (the number of volatile threads can equal the difference between the ServiceMaxThread and ServiceMinThread values). A volatile thread will be stopped after being in the 'Ready' state for more than 1 to 3 minutes.
tcbad: The address of the TCB running the thread.
rpc: The number of RPCs run on this thread.
cpu_used: The amount of CPU consumed on this thread, expressed in seconds.
|
| |
System action:
|
This message gives detailed information per thread as a result of the CNTL STATUS SHOW=ALL console command.
|
| |
User response:
|
None.
|
|
VAIS196I
|
Service is currently ****Unavailable****
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message follows messages VAIS181I/182I/183I if the status of the service is 'stopped'.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS197E
|
xxxxxxxx Thread for User(uuuuuuuu) with Thrdid(tttttttt) at (termid) purged due to timeout.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Thread exceeded Idletime.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS200E
|
Start thread request for service name from user ID at terminal ID rejected.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
A request to establish a connection to the z/OS server from the stated user at the stated terminal was rejected. This message is always followed by another VAIS20xE message that supplies the reason for the rejection.
|
| |
System action:
|
The connection request is rejected.
|
| |
User response:
|
Check the subsequent VAIS20xE messages relating to the given user and terminal and respond accordingly.
|
|
VAIS201E
|
** Unknown service name.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
A request to establish a connection to the server from a specific user at a specific terminal was rejected because the service that was specified in the connection request was not known to the z/OS server. This message is always preceded by a VAIS200E message which denotes the user and terminal who made the request.
|
| |
System action:
|
The connection request is rejected.
|
| |
User response:
|
Check the connection string that is being used at the specified terminal. Correct it and retry your connection request. Refer to SequeLink Administrator's Guide for details about the link parameters required when connecting to a z/OS server using each of the different network protocols supported.
|
|
VAIS202E
|
** Security Enabled in STRTTHRD, no longer supported.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
The connection is rejected.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS206S
|
** @VAIGM failure (insufficient storage).
|
| |
Severity:
|
Severe
|
| |
Explanation:
|
A request to establish a connection to the server from a specific user at a specific terminal was not satisfied due to an internal error in the server's start thread process.
|
| |
System action:
|
The connection request is rejected.
|
| |
User response:
|
Contact DataDirect Technologies technical support. Have a listing of the current server SIL ready to review. This error could be caused by an incorrect update to a DSASIZE parameter.
|
|
VAIS207T
|
ESTAEX recovery for nnnnnnnn setup
|
| |
Severity:
|
Trace
|
| |
Explanation:
|
ESTAEX recovery is activated on Workerthread nnnnnnnn.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS208E
|
Tttttttt - Maxcpu has been exceeded for this connection, CPU usage ssss secs.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
When DataSourceMaxCpuTime has been exceeded, this message shows the offending ThreadId and the number of CPU seconds consumed until now.
|
| |
System action:
|
If DataSourceMaxCpuAction is set to ABORT, the connection will be abended also.
|
| |
User response:
|
Determine why this connection consumed so much CPU usage.
|
|
VAIS209T
|
Start Thread for Service(ssssssss) at terminal(termid) for user(uuuuuuu) queued.
|
| |
Severity:
|
Trace
|
| |
Explanation:
|
A request to establish a connection to the server from the stated user at the stated terminal was successfully validated by the server's start thread process. The service request (identified by its service name) has been queued to the server's SCT for further validation.
|
| |
System action:
|
The connection request is queued to the SCT.
|
| |
User response:
|
None.
|
| |
User response:
|
Check why thread exceeds limit specified.
|
|
VAIS215E
|
Task tttttttt has unexpectedly terminated: (CC=xxxyyy) - attempting restart/reload.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The parameter defined for DB2INTERFACE in the SYSINI file does not match the value set in the SequeLink startup JCL file, RUNSRVR, or, the DD statement with the value for DB2INTERFACE is missing from the RUNSRVR file.
|
| |
System action:
|
Task is terminated.
|
| |
User response:
|
Change the DB2INTERFACE parameter value in the SequeLink startup JCL file, RUNSRVR, to the value set in the SYSINI file. For example, if the SYSINI file sets DB2INTERFACE=DB2A, the RUNSRVR JCL file should have a DD statement similar to the following:
|
|
VAIS216F
|
Task xxxxxxxx has unexpectedly terminated (CC=cc) restart/reload count Exhausted.
|
| |
Severity:
|
Fatal
|
| |
Explanation:
|
A critical task abended with CompletionCode cc and its restart Count, if any, is exhausted.
|
| |
System action:
|
The server abends with abend U146.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS219E
|
EOT routine for Service service failed.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The ServiceEotExit that was called during end of task, failed.
|
| |
System action:
|
None.
|
| |
User response:
|
Check why this routine failed, and contact DataDirect Technologies technical support.
|
|
VAIS220I
|
Application(nnnnnnnn) Status(xx) Debug(y).
|
| |
Severity:
|
Information
|
| |
Explanation:
|
This message is output following a CNTL STATUS SHOW=servicename command. The message shows the loadmodule nnnnnnnn information for the specified service.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS229E
|
CNTL REFRESH command obsolete.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
CNTL REFRESH command no longer supported.
|
| |
System action:
|
Command is ignored.
|
| |
User response:
|
None.
|
|
VAIS230T
|
Free storage below ______ K, above ____ K.
|
| |
Severity:
|
Trace
|
| |
Explanation:
|
Display free storage available above and below 16 MB.
|
| |
System action:
|
None.
|
| |
User response:
|
None. New connections will be refused if free storage drops below SosLimit values. See message VAIS018I.
|
|
VAIS233I
|
CNTL LIST command obsolete.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
CNTL LIST command no longer supported.
|
| |
System action:
|
Command is ignored.
|
| |
User response:
|
None.
|
|
VAIS235I
|
Free storage below ______ K, above ____ K.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Display free storage available above and below 16 MB. This message results from command CNTL LIST TYPE=FREE.
|
| |
System action:
|
None.
|
| |
User response:
|
None. New connections will be refused if free storage drops below SosLimit values. See message VAIS018I.
|
|
VAIS246I
|
Time altered from 24.00.00 to xx.xx.xx date julian.date.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Message to indicate the start of a new day.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS300I
|
Mgr SQLNK.DataDirect.xxxx registered.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
SequeLink server is registered to RRS as a ResourceMgr with the name SQLNK.DataDirect.xxxx where xxxx is the GlobalSubSystemId the server is started with.
|
| |
System action:
|
Registering to RRS during initialization.
|
| |
User response:
|
None.
|
|
VAIS301I
|
Mgr SQLNK.DataDirect.xxxx unregistered.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
SequeLink server unregistered from RRS.
|
| |
System action:
|
Unregisters from RRS during shutdown.
|
| |
User response:
|
None.
|
|
VAIS302I
|
Begin restart Mgr SQLNK.DataDirect.xxxx.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
SequeLink server is restarting as a ResourceMgr to RRS.
|
| |
System action:
|
Restarting as ResourceMgr during initialization.
|
| |
User response:
|
None.
|
|
VAIS303I
|
Incomplete Interest for URid(urid) Urstate(In-Urstate) Role(xxxx).
|
| |
Severity:
|
Information
|
| |
Explanation:
|
During a restart as a ResourceMgr, Incomplete Interest(s), which were unresolved when SequeLink was last unregistered, can be retrieved from RRS.
|
| |
System action:
|
Remember Urstate for this urid.
|
| |
User response:
|
None.
|
|
VAIS304I
|
Mgr has nnn Incomplete Interest(s) outstanding.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
During a restart, nnn Incomplete Interest(s) were retrieved.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS305I
|
Mgr SQLNK.DataDirect.xxxx restarted.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
SequeLink Server is restarted successfully as ResourceMgr to RSS.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS306E
|
Unable to construct a valid Mgr_name, Subsystemid is missing.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink Server must construct a unique ResourceMgr name to register to RRS. The GlobalSubSysId is required to qualify the string 'SQLNK.DataDirect'.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Supply a unique GlobalSubSysId or use CAF DB2 attachment.
|
|
VAIS307E
|
Mgr SQLNK.DataDirect.xxx registration failed, reason(xxxx).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink registration to RSS failed, see reasoncode xxxx.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS308E
|
Define Exit_routines to Context_mgr failed, reason(xxxx).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink registration to Context Mgr failed, reasoncode xxxx during RSS registration.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS309E
|
Define Exit_routines to RRS_mgr failed, reason(xxxx).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink registration to RRS_services failed, reasoncode xxxx during RRS registration.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS310E
|
Begin Restart Mgr failed, reason (xxxx).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink Begin Restart Mgr failed, reasoncode xxxx during RRS registration.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS311E
|
Retrieve Incomplete Interest failed, reason (xxxx).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink Retrieve Incomplete Interest failed reasoncode xxxx, during RRS registration.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS312E
|
End Restart Mgr failed, reason (xxxx).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink End Restart Mgr failed, reasoncode xxxx during RRS registration.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS313E
|
Respond to Retrieved Interest failed, reason (xxxx) URid(urid).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink Respond to Retrieved Interest failed, reasoncode xxxx during RRS registration.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS314E
|
Mgr is already registered by another server, use a different SubSystemID.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The ResourceMgrName SQLNK.DataDirect.xxxx is already in use. Change the GlobalSubSysId for this server.
|
| |
System action:
|
The server abends with U130.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS315E
|
Unregistration for SQLNK.DataDirect.xxxx failed, reason (yyyy).
|
| |
Severity:
|
Error
|
| |
Explanation:
|
The ResourceMgrName SQLNK.DataDirect.xxxx failed to unregister.
|
| |
System action:
|
Server continues shutdown.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS330I
|
Notification Exit - xxxxxxxxxxxxx.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Notification Exit called, xxxxxxxxxxxxx explains why.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS331E
|
Notification Exit - No Global data.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
None.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS332E
|
Notification Exit - could not locate RRSM.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
None.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS333E
|
Notification Exit - TACB not found.
|
| |
Severity:
|
Error
|
| |
Explanation:
|
Internal error.
|
| |
System action:
|
None.
|
| |
User response:
|
Contact DataDirect Technologies technical support.
|
|
VAIS348I
|
WLM in Goal mode - Policy(xxxxxxxx) ServiceDefinition(yyyyyyyy)
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Shows the active Policy and ServiceDefinition when WLM is in Goal mode.
|
| |
System action:
|
Registers as a WorkManager to WLM when MVSGlobalWLMEnclaves is specified.
|
| |
User response:
|
User response: None
|
|
VAIS349I
|
WLM in Compatibility mode - IPS(xxxxxxxx) ICS(yyyyyyyy)
|
| |
Severity:
|
Information
|
| |
Explanation:
|
Shows the active IPS and ICS member when WLM is in compatibility mode.
|
| |
System action:
|
Registers as a WorkManager to WLM when MVSGlobalWLMEnclaves is specified.
|
| |
User response:
|
None.
|
|
VAIS350I
|
WLM Enclave support enabled - Type(VAI ) Name(yyyy)
|
| |
Severity:
|
Information
|
| |
Explanation:
|
When MVSGlobalWLMEnclaves is specified, this message means that SequeLink succesfully registered as a workmanager to WLM with Type(VAI) and Name = MVSGlobalSubSysId.
|
| |
System action:
|
SequeLink Server is enabled to use WLM enclaves.
|
| |
User response:
|
None.
|
|
VAIS351E
|
Error connecting to WLM - IWMCONN reasoncode(xxxxx)
|
| |
Severity:
|
Error
|
| |
Explanation:
|
MVSGlobalWLMEnclaves is specified, but SequeLink failed to register as a workmanager to WLM. The reasoncode for the IWMCONN macro is displayed.
|
| |
System action:
|
SequeLink Server is not enabled to use WLM enclaves.
|
| |
User response:
|
Check the reasoncode for IWMCONN. If necessary, contact DataDirect Technologies technical support.
|
|
VAIS355I
|
Disconnected from WLM as WorkManager.
|
| |
Severity:
|
Information
|
| |
Explanation:
|
During shutdown of SequeLink Server, SequeLink deregistered from WLM as a workmanager.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS356E
|
Error disconnecting from WLM - IWMDISC reasoncode(xxxxx)
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink failed to disconnect from WLM as workmanager. The reasoncode for the IWMDISC macro is displayed.
|
| |
System action:
|
SequeLink Server continues with shutdown.
|
| |
User response:
|
Check the reasoncode for IWMDISC macro. If necessary, contact DataDirect Technologies technical support.
|
|
VAIS357E
|
No ConnectionToken found - unable to disconnect from WLM
|
| |
Severity:
|
Error
|
| |
Explanation:
|
WLM ConnectionToken is invalid or not found.
|
| |
System action:
|
SequeLink Server could not disconnect from WLM.
|
| |
User response:
|
Internal SequeLink error. If necessary, contact DataDirect Technologies technical support.
|
|
VAIS360I
|
Server registered in Sysplex - ClusterName(cccccccccccccccccc)
|
| |
Severity:
|
Information
|
| |
Explanation:
|
If MVSGlobalClusterName is specified, this message is displayed when SequeLink Server succesfully registers into the Sysplex with ClusterName cccccccccccccccccc.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|
|
VAIS361E
|
Register Server in Sysplex - IWMSRSRG failed reasoncode(xxxx)
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink failed to register into the Sysplex. The reasoncode for the IWMSRSRG macro is displayed.
|
| |
System action:
|
SequeLink Server continues initialization, without registration into Sysplex.
|
| |
User response:
|
Check reasoncode for IWMSRSRG. If necessary, contact DataDirect Technologies technical support.
|
|
VAIS362E
|
Deregister Server from Sysplex - IWMSRDRS failed reasoncode(xxxx)
|
| |
Severity:
|
Error
|
| |
Explanation:
|
SequeLink failed to deregister from the Sysplex. The reasoncode for the IWMSRDRS macro is displayed.
|
| |
System action:
|
SequeLink Server continues shutdown.
|
| |
User response:
|
Check the reasoncode for IWMSRDRS. If necessary, contact DataDirect Technologies technical support.
|
|
VAIS363E
|
Server deregistered from Sysplex - ClusterName(cccccccccccccccccc)
|
| |
Severity:
|
Information
|
| |
Explanation:
|
If MVSGlobalClusterName is specified, SequeLink Server succesfully deregistered from the Sysplex with ClusterName cccccccccccccccccc.
|
| |
System action:
|
None.
|
| |
User response:
|
None.
|